Skip to content

chore(deps): update dependency semantic-release to v19 [security] #1163

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

chore(deps): update dependency semantic-release to v19 [security] #1163

wants to merge 1 commit into from

Conversation

@renovate
Copy link

@renovate renovate bot commented Jun 18, 2022 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release ^17.3.1 -> ^19.0.0 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2022-31051

Impact

What kind of vulnerability is it? Who is impacted?

Secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that are excluded from uri encoding by encodeURI. Occurrence is further limited to execution contexts where push access to the related repository is not available without modifying the repository url to inject credentials.

Patches

Has the problem been patched? What versions should users upgrade to?

Fixed in 19.0.3

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Secrets that do not contain characters that are excluded from encoding with encodeURI when included in a URL are already masked properly.

References

Are there any links users can visit to find out more?

For more information

If you have any questions or comments about this advisory:

Release Notes

semantic-release/semantic-release (semantic-release)

v19.0.3

Compare Source

Bug Fixes
  • log-repo: use the original form of the repo url to remove the need to mask credentials (#​2459) (58a226f), closes #​2449

v19.0.2

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the stable version (0eca144)

v19.0.1

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the latest beta version (8097afb)

v19.0.0

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the beta, which upgrades npm to v8 (f634b8c)
  • upgrade marked to resolve ReDos vulnerability (#​2330) (d9e5bc0)
BREAKING CHANGES
  • npm-plugin: @semantic-release/npm has also dropped support for node v15
  • node v15 has been removed from our defined supported versions of node. this was done to upgrade to compatible versions of marked and marked-terminal that resolved the ReDoS vulnerability. removal of support of this node version should be low since it was not an LTS version and has been EOL for several months already.

v18.0.1

Compare Source

Bug Fixes

v18.0.0

Compare Source

This is a maintenance release. An increasing amount of dependencies required a node version higher than the Node 10 version supported by semantic-release@17. We decided to go straight to a recent Node LTS version because the release build is usually independent of others, requiring a higher node version is less disruptive to users, but helps us reduce the maintenance overhead.

If you use GitHub Actions and need to bump the node version set up by actions/node-setup, you can use octoherd-script-bump-node-version-in-workflows

BREAKING CHANGES

node-version: the minimum required version of node is now v14.17

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from c44bbec to df086b6 Compare August 16, 2022 22:06
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from df086b6 to 1445347 Compare October 25, 2022 16:49
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to 19.0.3 [security] Update dependency semantic-release to 19.0.3 [SECURITY] Dec 17, 2022
@renovate renovate bot changed the title Update dependency semantic-release to 19.0.3 [SECURITY] chore(deps): update dependency semantic-release to 19.0.3 [security] Dec 17, 2022
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to 19.0.3 [security] chore(deps): update dependency semantic-release to v19 [security] Mar 16, 2023
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to 19.0.3 [security] Mar 16, 2023
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 1445347 to cd585d4 Compare March 16, 2023 22:26
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to 19.0.3 [security] chore(deps): update dependency semantic-release to v19 [security] Mar 17, 2023
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to 19.0.3 [security] Mar 17, 2023
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to 19.0.3 [security] chore(deps): update dependency semantic-release to v19 [security] Mar 20, 2023
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to 19.0.3 [security] Mar 22, 2023
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to 19.0.3 [security] chore(deps): update dependency semantic-release to v19 [security] Mar 30, 2023
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from cd585d4 to 913b4b9 Compare October 13, 2023 17:22
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 3 times, most recently from 9769698 to 366afac Compare February 26, 2024 20:13
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 366afac to 6e639af Compare March 13, 2024 18:05
@renovate
Copy link
Author

renovate bot commented Mar 13, 2024 •
edited
Loading

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @semantic-release/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"^19.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=15.8.0 <18.0.0" from @semantic-release/[email protected]
npm ERR! node_modules/@semantic-release/changelog
npm ERR!   dev @semantic-release/changelog@"^5.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   peer semantic-release@">=15.8.0 <18.0.0" from @semantic-release/[email protected]
npm ERR!   node_modules/@semantic-release/changelog
npm ERR!     dev @semantic-release/changelog@"^5.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-14T15_20_37_300Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-14T15_20_37_300Z-debug-0.log

@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from c359288 to 1ed90e8 Compare March 14, 2024 15:20
@renovate
Copy link
Author

renovate bot commented May 17, 2024 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @semantic-release/[email protected]
npm error Found: [email protected]
npm error node_modules/semantic-release
npm error   dev semantic-release@"^19.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer semantic-release@">=15.8.0 <18.0.0" from @semantic-release/[email protected]
npm error node_modules/@semantic-release/changelog
npm error   dev @semantic-release/changelog@"^5.0.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/semantic-release
npm error   peer semantic-release@">=15.8.0 <18.0.0" from @semantic-release/[email protected]
npm error   node_modules/@semantic-release/changelog
npm error     dev @semantic-release/changelog@"^5.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-06-19T16_07_02_690Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-06-19T16_07_02_690Z-debug-0.log

@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 2b9d46c to 8de38b1 Compare May 17, 2024 17:21
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 19c67df to f6bf249 Compare December 4, 2024 22:05
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from f6bf249 to 19d9f69 Compare January 15, 2025 14:21
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 19d9f69 to 0953267 Compare June 19, 2025 16:07
@renovate
Copy link
Author

renovate bot commented Jun 19, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 19.x releases. But if you manually upgrade to 19.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/npm-semantic-release-vulnerability branch June 19, 2025 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@CLAassistant @apaparazzi0329